Detecting a transceiver using a noise optical signal

ABSTRACT

A method may include causing a signal to be transmitted that includes a plurality of wavelengths. The signal may be transmitted via an optical fiber that is associated with a particular wavelength. The particular wavelength may be included in the plurality of wavelengths. The method may include filtering the signal, based on the particular wavelength, to generate a filtered signal. The filtered signal may include the particular wavelength. The method may include detecting the filtered signal in association with the optical fiber. The method may include determining the particular wavelength based on the filtered signal. The method may include storing or providing information identifying at least one of the particular wavelength, the optical fiber, or a transmitter that transmitted the signal.

BACKGROUND

Fiber-optic communication is a mechanism for transmitting informationfrom one place to another by sending pulses of light through an opticalfiber. The light forms an electromagnetic carrier wave that may bemodulated to carry information. Because of advantages over electricaltransmission, optical fibers have largely replaced copper wirecommunications in core networks. Optical fiber is used by manytelecommunications companies to transmit telephone signals, Internetcommunication, and cable television signals. The process ofcommunicating using fiber-optics involves the following basic steps:creating the optical signal using a transmitter, relaying the signalalong a fiber, ensuring that the signal does not become too distorted orweak, receiving the optical signal using a receiver, and converting theoptical signal into an electrical signal to determine informationcarried via the optical signal.

SUMMARY

According to some possible implementations, a method may include causinga signal to be transmitted that includes a plurality of wavelengths. Thesignal may be transmitted via an optical fiber that is associated with aparticular wavelength. The particular wavelength may be included in theplurality of wavelengths. The method may include filtering the signal,based on the particular wavelength, to generate a filtered signal. Thefiltered signal may include the particular wavelength. The method mayinclude detecting the filtered signal in association with the opticalfiber. The method may include determining the particular wavelengthbased on the filtered signal. The method may include storing orproviding information identifying at least one of the particularwavelength, the optical fiber, or a transmitter that transmitted thesignal.

According to some possible implementations, a system may include atransceiver comprising a transmitter and an amplifier to transmit anoise signal of a plurality of wavelengths when the transmitter does notspecify a wavelength. The system may include an optical fiber connectedwith the transceiver and transporting the noise signal. The opticalfiber may be associated with a particular wavelength. The system mayinclude a multiplexer to receive the noise signal via the optical fiber.The multiplexer may be connected to a plurality of optical fibers,including the optical fiber. The multiplexer may filter the plurality ofwavelengths based on the particular wavelength, and may pass a filteredsignal, of the particular wavelength, to an optical channel monitor. Theoptical channel monitor may detect the filtered signal and determine theparticular wavelength. A controller device may cause the amplifier totransmit the noise signal, and may determine that the filtered signal isassociated with the transceiver.

According to some possible implementations, a device may include one ormore processors. The one or more processors may cause an amplifier totransmit a noise signal via an optical fiber, of a plurality of opticalfibers. The one or more processors may detect the noise signal. The oneor more processors may determine that the noise signal is associatedwith the optical fiber and that the noise signal originates from theamplifier. The one or more processors may obtain information identifyinganother device, a particular wavelength, and another optical fiber, of aplurality of other optical fibers. The one or more processors mayconfigure the amplifier to transmit a signal of the particularwavelength. The one or more processors may configure the device totransmit the signal of the particular wavelength toward the other deviceand the other optical fiber.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIGS. 2A-2C are diagrams of an example environment in which systemsand/or methods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for identifying atransceiver based on a noise signal;

FIGS. 5A-5C are diagrams of an example implementation relating to theexample process shown in FIG. 4;

FIG. 6 is a flow chart of an example process for configuring local andremote network devices; and

FIGS. 7A-7E are diagrams of an example implementation relating to theexample process shown in FIG. 4.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A network device may include a variety of optical fibers connected to amultiplexer. Signals, received via the variety of optical fibers, may befiltered to particular wavelengths corresponding to each of the varietyof optical fibers. When connecting a transceiver to a particular opticalfiber, the network device may need to determine a particular wavelengthcorresponding to the particular optical fiber. However, based on themultiplexer filtering wavelengths other than the particular wavelength,determining the particular wavelength may be time consuming.Implementations described herein enable the network device to moreefficiently determine the particular wavelength by transmitting a noisesignal including a variety of wavelengths, and improve efficiency ofimplementing multiple network devices (e.g., by performing a “plug andplay” configuration of the multiple network devices).

FIGS. 1A-1C are diagrams of an overview of an example implementation 100described herein. Assume that FIGS. 1A-1C show a network device thatincludes a transceiver, a multiplexer (e.g., a “Mux”) with fiveconnected optical fibers, and an optical channel monitor.

As shown in FIG. 1A, each of the five optical fibers may be associatedwith a particular wavelength based on corresponding multiplexer ports.Here, a first optical fiber is associated with a wavelength of λ₁, asecond optical fiber is associated with a wavelength of λ₂, a thirdoptical fiber is associated with a wavelength of λ₃, a fourth opticalfiber is associated with a wavelength of λ₄, and a fifth optical fiberis associated with a wavelength of λ₅. Assume that the multiplexer portswill filter, from each optical signal, wavelengths other than theassociated wavelength. For example, the multiplexer will only passoptical signals with a wavelength of λ₁ via the multiplexer portassociated with the wavelength of λ₁, and so on. As shown, thetransceiver is connected to the optical fiber that is associated withthe wavelength of λ₃. As further shown, neither the transceiver nor theoptical channel monitor are aware that the transceiver is connected tothe optical fiber associated with the wavelength of λ₃.

As shown in FIG. 1B, if the transceiver does not transmit a noise signalincluding a variety of wavelengths, the transceiver may iterativelytransmit signals of different wavelengths to determine a correct opticalsignal wavelength. As shown, the transceiver may first transmit a signalwith a wavelength of λ₁, and may determine that the signal is filteredby the multiplexer. As further shown, the transceiver may secondtransmit a signal with a wavelength of λ₂, and may determine that thesignal is filtered by the multiplexer. As shown, the transceiver maythird transmit a signal with a wavelength of λ₃, and may determine thatthe signal is passed by the multiplexer. Assume that the optical channelmonitor detects the signal and transmits information identifying thewavelength of λ₃ to the transceiver. As described in FIG. 1B, theprocess of determining the correct optical signal wavelength may be timeconsuming and inefficient.

As shown in FIG. 1C, rather than iteratively transmitting signals ofdifferent wavelengths, the transceiver may transmit a noise signal intothe fiber that is associated with the wavelength of λ₃ that includeseach of the wavelengths (e.g., λ₁, λ₂, λ₃, λ₄, and λ₅). As furthershown, the multiplexer may filter the signal based on the wavelength ofλ₃, and may pass an optical signal including only the wavelength of λ₃.

As shown, the optical channel monitor may scan the optical fibers, andmay detect the filtered optical signal with the wavelength of λ₃. Assumethat the optical channel monitor provides configuration information,identifying the wavelength of λ₃, to the transceiver. As shown, based onthe configuration information, the transceiver may transmit opticalsignals with a wavelength of λ₃, which may pass the multiplexer and berouted, by the network device, to a destination (e.g., a remote networkdevice).

Implementations described herein may enable the network device todetermine a particular wavelength at which to transmit an optical signalvia an optical fiber of a multiplexer. By transmitting a noise signalthat includes multiple different wavelengths via the optical fiber, thenetwork device may reduce an amount of time and/or effort required todetermine the particular wavelength (e.g., based on the multiplexerfiltering wavelengths other than the particular wavelength).Implementations described herein may provide configuration information,to the transceiver or another device, based on determining theparticular wavelength, which improves efficiency and reduces timeconsumption when implementing the network device, or other networkdevices, in an optical network.

FIGS. 2A-2C are diagrams of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2A, environment 200 may include a network management device 202, anoptical network 204, and one or more network devices 206-1 through 206-N(N≥1) (hereinafter referred to collectively as “network devices 206,”and individually as “network device 206”). Devices of environment 200may interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Network management device 202 may include one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with a network (e.g., optical network 204). For example,network management device 202 may include a computing device, such as aserver or a similar type of device. Network management device 202 mayassist a user in modeling and/or planning a network, such as opticalnetwork 204. For example, network management device 202 may assist inmodeling and/or planning an optical network configuration, which mayinclude quantities, locations, capacities, parameters, and/orconfigurations of network devices 206. In some implementations, networkmanagement device 202 may be associated with a user interface. In someimplementations, network management device 202 may be a distributeddevice associated with one or more network devices 206. For example,network management device 202 may be included in a controller device 210of one or more network devices 206. In some implementations, networkmanagement device 202 may be separate from network device 206, but maybe linked to network device 206 via a protocol interface, such as anapplication programming interface, or the like.

Optical network 204 may include any type of network that uses light as atransmission medium. For example, optical network 204 may include afiber-optic based network, an optical transport network, alight-emitting diode network, a laser diode network, an infrarednetwork, an optical amplifier and/or a combination of these or othertypes of optical networks. Optical network 204 may include one or moreoptical routes (e.g., optical lightpaths) that may specify a route alongwhich light is carried (e.g., using one or more optical links) betweentwo or more network devices 206 (e.g., via an optical link) and may alsoinclude one or more monitoring devices, such as an optical channelmonitor (OCM). An optical link may include an optical fiber, an opticalcontrol channel, an optical data channel, or the like, and may carry anoptical signal (e.g., a signal associated with a particular wavelengthof light), an optical super-channel (e.g., a set of optical signals), asuper-channel set, an optical carrier set, a set of spectral slices, orthe like.

Network device 206 may include one or more devices capable of receiving,generating, storing, processing, and/or providing data carried by anoptical signal via an optical link. For example, network device 206 mayinclude one or more optical data processing and/or optical traffictransfer devices, such as an optical amplifier (e.g., a doped fiberamplifier, an erbium doped fiber amplifier, a Raman amplifier, etc.), anoptical add-drop multiplexer (OADM) (e.g., a reconfigurable opticaladd-drop multiplexer (ROADM), a flexibly reconfigurable optical add-dropmultiplexer (“FROADM”) that may utilize a flexible wavelength grid,etc.), an optical source device (e.g., a laser source), an opticaldestination device (e.g., a laser sink), an optical multiplexer, anoptical demultiplexer, an optical transmitter, an optical receiver, anoptical transceiver, a photonic integrated circuit (PIC), an integratedoptical circuit, or the like. In some implementations, network device206 may include one or more optical components. Network device 206 mayprocess and/or transmit an optical signal (e.g., to another networkdevice 206 via an optical link) to deliver the optical signal throughoptical network 204.

As shown in FIG. 2B, network device 206 may include a multiplexer 208, acontroller device 210, an optical supervisory channel (OSC) 212, anoptical channel monitor (OCM) 214, a demultiplexer 216, and atransceiver 218.

Multiplexer 208 may include, for example, an optical multiplexer (e.g.,a power multiplexer, a WSS-based multiplexer, a multi-cast multiplexer,or the like) that combines multiple input channels for transmission viaan output fiber. For example, multiplexer 208 may combine multipleoptical signals received via multiple optical fibers, and may providethe combined signals to another device via an optical link (e.g., afiber). In some implementations, multiplexer 208 may filter opticalsignals. For example, multiplexer 208 may include an array waveguidegrating (AWG) that filters optical signals based on particularwavelengths.

Controller device 210 may include, for example, one or more devicescapable of receiving, generating, storing, processing, and/or providinginformation associated with network device 206. For example, controllerdevice 210 may include a server, an application-specific integratedcircuit, or the like. Controller device 210 may cause components ofnetwork device 206 to perform operations. For example, controller device210 may cause transmitter 220 to generate an optical signal of aparticular wavelength, may cause amplifier 224 to amplify an opticalsignal (e.g., an optical signal of the particular wavelength, a noisesignal, etc.), or the like. In some implementations, controller device210 may receive configuration information from another device (e.g., OCM214, remote network device 206-2, etc.) and may cause the components ofnetwork device 206 to perform the operations based on the configurationinformation. In some implementations, controller device 210 may performoperations related to configuring optical network 204 and/or networkdevice 206 (e.g., routing network traffic based on configurationinformation, determining whether an optical signal, detected by OCM 214,is associated with transceiver 218, etc.).

OSC 212 may include, for example, an amplifier, an emitter, or the like,that emits and/or receives a signal (e.g., an optical signal) on aparticular channel (e.g., a particular wavelength) via which networkdevices 206 may communicate. OSC 212 may be associated with a particularwavelength, in some implementations. Network management device 202and/or controller device 210 may provide information to, receiveinformation from, and/or cause information to be provided betweennetwork devices 206 via OSC 212. In some implementations, network device206-1 may provide information (e.g., a network address associated withnetwork device 206-1, a network address associated with transceiver 218,an optical wavelength of a signal, a multiplexer port number, etc.) tonetwork device 206-2 via OSC 212, or may receive information fromnetwork device 206-2 via OSC 212.

OCM 214 may include, for example, a device that detects an opticalsignal and determines a wavelength associated with the optical signal.For example, OCM 214 may include a photodetector, or a group ofphotodetectors. OCM 214 may monitor (e.g., scan, sweep, etc.) ports ofmultiplexer 208, and may detect an optical signal, transmitted bytransceiver 218 and/or filtered by multiplexer 208. OCM 214 maydetermine a wavelength associated with the detected optical signal.

Demultiplexer 216 may include, for example, an optical de-multiplexer(e.g., a power demultiplexer, a WSS-based demultiplexer, an AWG, or thelike) that separates optical signals 226 carried over an input fiber.For example, demultiplexer 216 may separate a multiplexed optical signalinto constituent optical signals, and may provide each of theconstituent optical signals 226 to a corresponding transceiver 218.

As shown in FIG. 2C, transceiver 218 may include, for example, atransmitter 220, a receiver 222, and an amplifier 224. Transceiver 218may transmit an optical signal to multiplexer 208, and may receive anoptical signal from demultiplexer 216.

Transmitter 220 may include, for example, an optical transmitter and/oran optical transceiver that generates an optical signal when a voltageor current is applied. For example, transmitter 220 may include one ormore integrated circuits, such as a transmitter photonic integratedcircuit (PIC), an application specific integrated circuit (ASIC), or thelike. In some implementations, transmitter 220 may include a laserassociated with each wavelength associated with transmitter 220, adigital signal processor to process digital signals, a digital-to-analogconverter to convert the digital signals to analog signals, a modulatorto modulate the output of the laser, and/or a multiplexer to combineeach of the modulated outputs (e.g., to form a combined output or WDMsignal). In some implementations, transmitter 220 may be tuned totransmit an optical signal of a particular wavelength based onconfiguration information that identifies the particular wavelength.

Receiver 222 may include, for example, an optical receiver and/or anoptical transceiver that generates an electrical signal based on areceived optical signal. For example, receiver 222 may include one ormore integrated circuits, such as a receiver PIC, an ASIC, or the like.In some implementations, receiver 222 may include a photodetector toconvert an optical signal to a voltage signal, an analog-to-digitalconverter to convert voltage signals to digital signals, and/or adigital signal processor to process the digital signals. In someimplementations, a single receiver 222 may be associated with a singleoptical signal. In some implementations, a single receiver 222 may beassociated with multiple optical signals, or multiple receivers 222 maybe associated with a single optical signal. In some implementations,receiver 222 may be tuned to receive an optical signal of a particularwavelength based on configuration information that identifies theparticular wavelength.

Amplifier 224 may include an amplifying device, or a collection ofamplifying devices. In some implementations, amplifier 224 may includean amplifier that may directly amplify an input optical signal (e.g., asignal supplied by transmitter 220). In some implementations, amplifier224 may include a variable optical amplifier (VOA), a semiconductoroptical amplifier (SOA), a doped fiber amplifier (e.g., an erbium-dopedfiber amplifier, an erbium-doped waveguide amplifier, etc.). In someimplementations, amplifier 224 may include another type of light sourcethat is capable of providing a noise signal (e.g., a light-emittingdiode, etc.). When a voltage or current is applied to amplifier 224,amplifier 224 may amplify an optical signal received from transmitter220. When a voltage or current is applied to amplifier 224 withoutamplifier 224 receiving an optical signal from transmitter 220,amplifier 224 may generate a noise signal (e.g., a white noise signal,etc.) that includes a set of wavelengths.

The number and arrangement of devices and networks shown in FIGS. 2A-2Care provided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIGS. 2A-2C. Furthermore, two or more devices shown in FIGS.2A-2C may be implemented within a single device, or a single deviceshown in FIGS. 2A-2C may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) of network 200 may perform one or more functions describedas being performed by another set of devices of network 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to network management device 202 and/or controller device210. In some implementations, network management device 202 and/orcontroller device 210 may include one or more devices 300 and/or one ormore components of device 300. As shown in FIG. 3, device 300 mayinclude a bus 310, a processor 320, a memory 330, a storage component340, an input component 350, an output component 360, and acommunication interface 370.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 mayinclude a processor (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), an accelerated processing unit (APU), etc.), amicroprocessor, and/or any processing component (e.g., afield-programmable gate array (FPGA), an application-specific integratedcircuit (ASIC), etc.) capable of receiving and/or executinginstructions. In some implementations, processor 320 can be programmedto perform a function. Memory 330 may include a random access memory(RAM), a read only memory (ROM), and/or another type of dynamic orstatic storage device (e.g., a flash memory, a magnetic memory, anoptical memory, etc.) that stores information and/or instructions foruse by processor 320.

Storage component 340 may store information and/or software related tothe operation and use of device 300. For example, storage component 340may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 350 may include a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 350may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 360 may include a component that provides outputinformation from device 300 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 370 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for identifying atransceiver based on a noise signal. In some implementations, one ormore process blocks of FIG. 4 may be performed by network device 206and/or components of network device 206. In some implementations, one ormore process blocks of FIG. 4 may be performed by another device or agroup of devices separate from or including network device 206, such asnetwork management device 202.

As shown in FIG. 4, process 400 may include receiving a noise signalthat includes a range of wavelengths via an optical fiber that isassociated with a particular wavelength of the range of wavelengths(block 410). For example, multiplexer 208 of network device 206 mayreceive a noise signal. Multiplexer 208 may receive the noise signalfrom transceiver 218, or from a component of transceiver 218 (e.g.,amplifier 224 of transceiver 218). Multiplexer 208 may receive the noisesignal via an optical fiber that is associated with a particularwavelength. For example, multiplexer 208 may filter optical signalsreceived via the optical fiber based on the particular wavelength, asdescribed in more detail below.

In some implementations, amplifier 224 may generate the noise signal.For example, when amplifier 224 receives an optical signal fromtransmitter 220, amplifier 224 may receive voltage or current, and mayamplify the received optical signal. In a situation where amplifier 224receives voltage or current and does not receive an optical signal fromtransmitter 220, amplifier 224 may generate and/or transmit the noisesignal. In some implementations, controller device 210 may causeamplifier 224 to generate the noise signal. For example, controllerdevice 210 may cause the voltage or current to be provided to amplifier224 (e.g., by transmitter 220, by network device 206, etc.) tofacilitate determination of the particular wavelength.

In some implementations, controller device 210 may record a time valueof a transmission time associated with the noise signal. For example,based on causing amplifier 224 to generate and transmit the noisesignal, controller device 210 may store information associating thenoise signal with a transmission time. Controller device 210 may comparethe transmission time to a time value of a receipt time determined basedon OCM 214 receiving a filtered signal, to determine whether thefiltered signal is related to the noise signal, as described in moredetail elsewhere herein.

Network device 206 and/or transceiver 218 may be associated with anetwork address, such as an Internet Protocol (IP) address or the like.When configuring transceiver 218, network device 206 may provide thenetwork address to another device. For example, local network device206-1 may provide a first network address to remote network device206-2, which may perform configuration operations as described herein,and remote network device 206-2 may provide a second network address tolocal network device 206-1. Based on the first network address and thesecond network address, local network device 206-1 and remote networkdevice 206-2 may communicate.

The noise signal may include light, of a range of wavelengths, a set ofwavelengths, or the like. In some implementations, the noise signal mayinclude a white noise signal (e.g., an optical signal including aconstant power spectral density). For example, amplifier 224 maygenerate a noise signal when receiving voltage or current withoutreceiving an optical signal from transmitter 220, and the noise signalmay include a range of wavelengths. The particular wavelength,associated with the optical fiber of multiplexer 208, may be included inthe range of wavelengths. In this way, multiplexer 208 may pass theparticular wavelength, which permits OCM 214 to detect the particularwavelength, and, thus, associate transceiver 218 with the particularwavelength and/or the optical fiber.

In some implementations, amplifier 224 may generate the noise signal toenable network device 206 to determine the particular wavelength of theoptical fiber to which transceiver 218 is connected. For example, wheninstalling network device 206, a technician may connect transceiver 218to a particular optical fiber, of a set of optical fibers of multiplexer208. The particular optical fiber may be associated with a particularwavelength. When multiplexer 208 receives an optical signal via theparticular optical fiber, multiplexer 208 may filter wavelengths oflight other than the particular wavelength (e.g., may pass theparticular wavelength), as described in more detail below.

The technician and/or transceiver 218 may not know the particularwavelength, which may hinder implementation of network device 206. Forexample, the technician may select an available optical fiber to connectwith network device 206, without knowing the particular wavelengthassociated with the available optical fiber. To determine the particularwavelength, network device 206 may iteratively check wavelengths untildetermining the particular wavelength that passes multiplexer 208, whichmay be time consuming. By generating the noise signal, which may includethe particular wavelength, amplifier 224 may permit OCM 214 to detect afiltered signal of the particular wavelength after multiplexer 208passes the filtered signal of the particular wavelength. This reduceseffort and/or planning required to determine the particular wavelengthand, thus, conserves resources.

In some implementations, controller device 210 may refer toconfiguration information, related to network device 206 and/ortransceiver 218, to determine a configuration of transceiver 218. Forexample, if a transceiver 218 of remote network device 206-2 isassociated with a particular optical fiber, a particular wavelength, aparticular multiplexer port, a or the like, local network device 206-1may refer to configuration information associated with remote networkdevice 206-2 to determine the particular optical fiber and/or theparticular wavelength. In some implementations, local network device206-1 may obtain the configuration information (e.g., from controllerdevice 210, from network management device 202, etc.).

In some implementations, controller device 210, of local network device206-1 may obtain configuration information from remote network device206-2, as described in more detail in connection with FIG. 6, below. Forexample, controller device 210 may obtain the configuration informationto determine a particular optical fiber, of local network device 206-1,to connect with transceiver 218. As another example, controller device210 may obtain the configuration information to determine a networkaddress, associated with remote network device 206-2, based on which toroute fiber optic network traffic to and/or from remote network device206-2. In some implementations, controller device 210 may obtain theconfiguration information via OSC 212.

As further shown in FIG. 4, process 400 may include filtering the noisesignal to remove wavelengths other than the particular wavelength (block420). For example, multiplexer 208 (e.g., an array waveguide grating ofmultiplexer 208) may filter optical signals received via each opticalfiber according to the corresponding particular wavelength of theoptical fiber. For example, if an optical fiber is associated with aparticular wavelength of 1551.32 nanometers (nm), multiplexer 208 mayfilter signals, received via the optical fiber, of wavelengths otherthan 1551.32 nm. As another example, if the optical fiber receives anoise signal of 600 nm-1500 nm, multiplexer 208 may filter the noisesignal, and may pass an optical signal of 1551.32 nm to OCM 214 oranother device.

In some implementations, multiplexer 208 may be programmed to pass aparticular wavelength of the noise signal. For example, multiplexer 208may include a reconfigurable optical add-drop multiplexer (ROADM), orthe like. Unused ports, of multiplexer 208, may be programmed to passlight at different wavelengths. In such cases, when a noise signal istransmitted via a particular port that is associated with a particularwavelength, multiplexer 208 may filter the noise signal to theparticular wavelength. OCM 214 may detect the filtered noise signal atthe particular wavelength, and controller device 210 may associate thedetected noise signal with the particular port based on informationassociating the particular port with the particular wavelength. Forexample, controller device 210 may associate the filtered noise signalwith a network address of the particular port, such as a multiplexerport identifier, or the like.

In some implementations, controller device 210 may provide themultiplexer port identifier and/or a network address of local networkdevice 206-1 and/or transceiver 218 to remote network device 206-2. Forexample, remote network device 206-2 may include a ROADM, and remotenetwork device 206-2 may configure the ROADM based on the multiplexerport identifier and/or the network address of local network device206-1/transceiver 218. In such cases, local network device 206-1 andremote network device 206-2 may communicate to assign a particularwavelength and/or time slot to communications between local networkdevice 206-1 and remote network device 206-2.

As further shown in FIG. 4, process 400 may include detecting thefiltered signal at the particular wavelength (block 430). For example,multiplexer 208 may filter the noise signal according to a particularwavelength, and may pass a filtered signal of the particular wavelengthto OCM 214. OCM 214 may detect the filtered signal, and may determinethe particular wavelength of the filtered signal. In someimplementations, OCM 214 may determine a receipt time of receiving thefiltered signal, which may aid controller device 210 to identify aparticular transceiver 218 that transmits the unfiltered noise signal.In some implementations, OCM 214 may determine connection informationbased on detecting the filtered signal, such as a multiplexer port, aparticular optical fiber, a time slot for transceiver 218, or the like.

As further shown in FIG. 4, process 400 may include determining that atransceiver is associated with the filtered signal (block 440). Forexample, OCM 214 may determine a receipt time of receiving the filteredsignal. OCM 214 may provide information identifying the receipt time toanother device (e.g., network management device 202, controller device210, etc.). Transceiver 218 may transmit the noise signal at aparticular transmission time, and another device (e.g., networkmanagement device 202, controller device 210, etc.) may storeinformation identifying the transmission time. Network management device202 and/or controller device 210 may compare the transmission time andthe receipt time to determine whether transceiver 218 transmitted thenoise signal. In some implementations, OCM 214 may determine a directionto associate with the filtered signal (e.g., east, west, etc.), such aswhen network device 206 is included in an optical network 204 of aring-based configuration.

In some implementations, OCM 214 may receive multiple filtered signals.For example, a technician may connect multiple transceivers 218 tomultiple optical fibers. Each transceiver 218 may transmit a noisesignal into the corresponding optical fiber. In some implementations,the transceivers 218 may transmit the noise signals at differenttransmission times, and OCM 214 may receive the corresponding filteredsignals at different receipt times. In such implementations, controllerdevice 210 may identify which transceiver 218 is associated with each ofthe optical fibers by comparing the different transmission times to thedifferent receipt times.

Additionally, or alternatively, controller device 210 may selectivelyactivate and/or deactivate transceivers 218 to associate thetransceivers 218 with optical fibers. For example, controller device 210may cause a first transceiver 218 to emit a noise signal, and may matchthe first transceiver 218 to a first optical fiber based on OCM 214receiving a first filtered signal (e.g., of a first wavelength).Controller device 210 may deactivate the first transceiver 218, and maycause a second transceiver 218 to emit a noise signal. Controller device210 may match the second transceiver 218 to a second optical fiber basedon OCM 214 receiving a second filtered signal (e.g., of a secondwavelength that is different than the first wavelength, of the firstwavelength, etc.).

As further shown in FIG. 4, process 400 may include storing and/orproviding configuration information regarding the particular opticalfiber, the particular wavelength, and/or the transceiver (block 450).For example, controller device 210 may store and/or provideconfiguration information regarding the particular optical fiber, theparticular wavelength, and/or the transceiver. In some implementations,network management device 202 may provide and/or store the configurationinformation. In some implementations, controller device 210 may receive,store and/or provide configuration information to perform “plug andplay” configuration operations without preemptively planning particularmultiplexer ports to which to connect the set of network devices 206,which reduces expense and improves reliability of configuration of theset of network devices 206.

In some implementations, controller device 210 may provide configurationinformation to transceiver 218. For example, controller device 210 mayprovide information identifying the particular wavelength of the opticalfiber to which transmitter 220 is connected, which may cause transmitter220 to transmit an optical signal of the particular wavelength toamplifier 224. Amplifier 224 may amplify the optical signal of theparticular wavelength, and may provide the amplified optical signal tonetwork device 206 for transmission. In this way, network device 206 mayuse a noise signal to determine a particular wavelength of an opticalfiber to which transceiver 218 is connected, which conserves time and/orprocessing resources of components of network device 206. In someimplementations, controller device 210 may determine a particulardirection to associate with the noise signal. For example, in someimplementations, local network device 206-1 and remote network device206-2 may be included in an optical network 204 of a ring-basedconfiguration. In such an optical network 204, network devices 206 mayroute traffic in a first direction around the ring-based optical network(e.g., clockwise, west, etc.), or in a second direction around thering-based optical network (e.g., counterclockwise, east, etc.).Controller device 210 of local network device 206-1 may determine aparticular direction, which may be associated with an optical fiberand/or a particular wavelength of the optical fiber, a noise signal, orthe like. Local network device 206-1 may communicate the particulardirection to remote network device 206-2 (e.g., in association with theconfiguration information), and network device 206-2 (e.g., controllerdevice 210, etc.) may configure remote network device 206-2 and/ortransceiver 218 based on the particular direction. In this way,controller device 210 may communicate a particular direction toassociate with a noise signal, an optical fiber, a particularwavelength, or the like, which permits controller device 210 to moreefficiently configure optical network 204.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIGS. 5A-5C are diagrams of an example implementation 500 relating toexample process 400 shown in FIG. 4. FIGS. 5A-5C show an example ofidentifying an optical fiber connection based on a noise signal. Assumethat devices shown in FIGS. 5A-5C (e.g., multiplexer 208, controllerdevice 210, OCM 214, transceiver 218, etc.) are components of aparticular network device 206, referred to as a local network device206. Assume further that the local network device 206 is communicative,via one or more optical fibers, with a remote network device 206 thatincludes the components and/or devices shown in FIGS. 2B and 2C.

As shown in FIG. 5A, and by reference number 505, multiplexer 208 may beassociated with a set of optical fibers (e.g., Optical Fiber 1 throughOptical Fiber 8). As shown, each of Optical Fiber 1 through OpticalFiber 8 may be associated with a different wavelength of optical signal.Here, Optical Fiber 1 is associated with a wavelength of λ₁32 1550.12nm, Optical Fiber 2 is associated with a wavelength of λ₂=1550.52 nm,Optical Fiber 3 is associated with a wavelength of λ₃=1550.92 nm,Optical Fiber 4 is associated with a wavelength of λ₄=1551.32 nm,Optical Fiber 5 is associated with a wavelength of λ₅=1551.72 nm,Optical Fiber 6 is associated with a wavelength of λ₆=1552.12 nm,Optical Fiber 7 is associated with a wavelength of λ₇=1552.52 nm, andOptical Fiber 8 is associated with a wavelength of λ₈=1552.92 nm. Insome implementations, multiplexer 208 may include optical fibers thatare associated with additional wavelengths and/or different wavelengths.

Multiplexer 208 may filter optical signals that multiplexer 208 receivesvia Optical Fiber 1 through Optical Fiber 8 (e.g., based on aninteraction of the optical signals with an array waveguide grating,etc.). For example, if multiplexer 208 receives an optical signal of1550.12 nm via Optical Fiber 3, multiplexer 208 may not pass the opticalsignal of 1550.12 nm (e.g., based on Optical Fiber 3 being associatedwith a wavelength of 1550.92 nm). As shown by reference number 510,transceiver 218 may be connected to Optical Fiber 4.

As shown in FIG. 5B, and by reference number 515, transmitter 220 maynot specify a particular wavelength of optical signal for amplifier 224to amplify. As shown by reference number 520, controller device 210 mayprovide voltage and/or current to amplifier 224. As shown by referencenumber 525, amplifier 224 may emit a noise signal including wavelengthsbetween 1520 nm and 1560 nm (e.g., λ_(w)=1520 nm-1560 nm). In someimplementations, the noise signal may include additional and/ordifferent wavelengths. As shown, the noise signal may travel via OpticalFiber 4 to multiplexer 208. As shown, amplifier 224 may transmit thenoise signal at a transmission time of 13:30:14. Assume that controllerdevice 210 stores information associating transceiver 218 and thetransmission time of 13:30:14.

As shown in FIG. 5C, multiplexer 208 may filter the noise signal. Here,assume that array waveguide grating of multiplexer 208 passes a filteredsignal of λ₄=1551.32 nm based on receiving the noise signal via OpticalFiber 4. As shown, multiplexer 208 may pass a filtered signal ofλ₄=1551.32 nm to OCM 214. As shown by reference number 530, OCM 214 maydetect the filtered signal in association with Optical Fiber 4, mayidentify the wavelength of λ₄=1551.32 nm, and may determine a receipttime of 13:30:14.

As shown by reference number 535, OCM 214 may provide informationidentifying Optical Fiber 4, the receipt time of 13:30:14, and thewavelength of λ₄=1551.32 nm to controller device 210. As shown byreference number 540, controller device 210 may determine whethertransceiver 218, shown in FIGS. 5A and 5B, transmitted the filteredsignal. As shown by reference number 545, controller device 210 maycompare the transmission time and the receipt time to determine that thetransmission time and the receipt time match. Assume that controllerdevice 210 determines that the receipt time occurs less than a thresholdamount of time after the transmission time (e.g., less than one secondafter, less than two seconds after, etc.).

As shown by reference number 550, based on the transmission timematching the receipt time, controller device 210 may determine thattransceiver 218 is connected to Optical Fiber 4, associated with thewavelength of λ₄=1551.32 nm. As shown by reference number 555,controller device 210 may configure transceiver 218. Assume thatcontroller device 210 configures transceiver 218 by causing transmitter220 to specify the wavelength of λ₄=1551.32 nm, and by causing amplifier224 to amplify the wavelength of λ₄=1551.32 nm. In this way, controllerdevice 210 may determine which optical fiber, of the set of opticalfibers associated with multiplexer 208, is connected to transceiver 218.By causing transceiver 218 to transmit the noise signal, controllerdevice 210 conserves time and/or power in determining the correspondingwavelength of the optical fiber.

As shown by reference number 560, controller device 210 may provideconfiguration information to remote network device 206. As shown,controller device 210 may provide the configuration information via OSC212. For example, OSC 212 may transmit the configuration information inan optical signal, via a particular wavelength, to be received by remotenetwork device 206-2. The configuration information may include, forexample, the wavelength of λ₄=1551.32 nm, a network address associatedwith local network device 206 and/or transceiver 218, or otherinformation. In some implementations, local network device 206-1 andremote network device 206-2 may perform configuration operations basedon the configuration information. For example, local network device206-1 and remote network device 206-2 may determine hardwareidentifiers, multiplexer port identifiers, and/or network addresses, andmay associate the network addresses with the hardware identifiers and/ormultiplexer port identifiers, as described in more detail in FIGS. 6 and7A-7E, below.

As indicated above, FIGS. 5A-5C are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 5A-5C.

FIG. 6 is a flow chart of an example process 600 for configuring localand remote network devices. In some implementations, one or more processblocks of FIG. 6 may be performed by network device 206 and/orcomponents of network device 206 (e.g., controller device 210-1 of localnetwork device 206-1 and/or controller device 210-2 of remote networkdevice 206-2). In some implementations, one or more process blocks ofFIG. 6 may be performed by another device or a group of devices separatefrom or including network device 206, such as network management device202.

As shown in FIG. 6, process 600 may include connecting a localtransceiver to a local optical fiber that is associated with aparticular wavelength and a multiplexer port identifier (block 610). Forexample, assume that local network device 206-1 and remote networkdevice 206-2 are to be connected via optical network 204. For localnetwork device 206-1 and remote network device 206-2 to communicate,local network device 206-1 and remote network device 206-2 may need toperform certain configuration actions. For example, local network device206-1 and remote network device 206-2 may need to determine a wavelengthat which to transmit optical signals, a multiplexer port to which toconnect, a network address (e.g., an IP address) of local network device206-1 and/or remote network device 206-2, a time slot in which totransmit optical signals of local network device 206-1 and remotenetwork device 206-2, or the like.

Transceiver 218 of local network device 206-1 may be connected to alocal optical fiber (e.g., a local optical fiber of local network device206-1) that is associated with a particular multiplexer port. Theparticular multiplexer port may filter optical signals to a particularwavelength, in some implementations. Therefore, local network device206-1 and remote network device 206-2 may need to transmit opticalsignals at the particular wavelength. However, it may be difficult for atechnician who is installing local network device 206-1 and/or remotenetwork device 206-2 to determine the particular wavelength.

To configure local network device 206-1 and remote network device 206-2,the technician may connect local network device 206-1 to an availablelocal optical fiber, irrespective of the wavelength and/or multiplexerport associated with the available local optical fiber. Based on beingconnected to the available local optical fiber, local network device206-1 may perform configuration operations to connect with remotenetwork device 206-2. For example, local network device 206-1 may checkwhether remote network device 206-2 is associated with configurationinformation (e.g., a time slot, a multiplexer port, an IP address, awavelength, etc.). If remote network device 206-2 is associated withconfiguration information, local network device 206-1 may be configuredbased on the configuration information. For example, transceiver 218 oflocal network device 206-1 may be connected to an identified multiplexerport, may perform Ethernet address resolution protocol with regard to anetwork address of remote network device 206-2, or the like.

As further shown in FIG. 6, process 600 may include determining theparticular wavelength and the multiplexer port identifier based on anoise optical signal (block 620). For example, if local network device206-1 determines that remote network device 206-2 is not associated withconfiguration information, local network device 206-1 may determine theparticular wavelength that is associated with the optical fiber and/or amultiplexer port identifier that identifies a multiplexer port to whichlocal network device 206-1 is connected. To determine the particularwavelength and the multiplexer port identifier, local network device206-1 may perform the operations described in connection with FIG. 4,above.

As further shown in FIG. 6, process 600 may include storing and/orproviding configuration information identifying the multiplexer portidentifier, the particular wavelength, and/or local connectioninformation (block 630). For example, based on determining theparticular wavelength, local network device 206-1 may store and/orprovide configuration information. The configuration information mayinclude a network address (e.g., an IP address, etc.) of local networkdevice 206-1, a time slot associated with local network device 206-1,the multiplexer port identifier and/or the particular wavelengthassociated with the local optical fiber, or the like.

In some implementations, local network device 206-1 may provideconfiguration information to remote network device 206-2. For example,local network device 206-1 may provide information identifying a networkaddress (e.g., an IP address, etc.) of local network device 206-1 and/ora modem associated with local network device 206-1, a multiplexer portidentifier of a multiplexer port with which transceiver 218 of localnetwork device 206-1 is connected, a particular wavelength associatedwith the multiplexer port, or the like. In some implementations, localnetwork device 206-1 may provide the information via OSC 212.Additionally, or alternatively, local network device 206-1 may providethe information to network management device 202, which may provide theinformation to remote network device 206-2.

By providing the configuration information to remote network device206-2, local network device 206-1 may permit remote network device 206-2to be configured based on the configuration information, which reducesexpense and time required to plan the configuration information beforeconnecting local network device 206-1 and remote network device 206-2.

As further shown in FIG. 6, process 600 may include connecting a remotetransceiver to a remote optical fiber that is associated with theparticular wavelength and the multiplexer port identifier based on theconfiguration information (block 640). For example, transceiver 218, ofremote network device 206-2 may be connected to a remote optical fiberassociated with remote network device 206-2 (e.g., by a technician,etc.). The remote optical fiber may be associated with the particularwavelength and/or multiplexer port identified by the configurationinformation. For example, if local network device 206-1 is connected tomultiplexer port 3, the configuration information may identifymultiplexer port 3, and transceiver 218 of remote network device 206-2may be connected to an optical fiber associated with multiplexer port 3.

As further shown in FIG. 6, process 600 may include testing whether theremote optical fiber is associated with the particular wavelength andthe multiplexer port identifier based on a noise optical signal (block650). For example, remote network device 206-2 may test whethertransceiver 218 of remote network device 206-2 is connected to thecorrect remote optical fiber and the correct multiplexer port bytransmitting a noise optical signal. To test whether transceiver 218 ofremote network device 206-2 is connected to the correct remote opticalfiber, remote network device 206-2 may perform operations described inmore detail in connection with FIG. 4, above.

As further shown in FIG. 6, process 600 may include storing and/orproviding configuration information identifying the multiplexer portidentifier, the particular wavelength, and/or remote connectioninformation (block 660). For example, remote network device 206-2 maystore and/or provide configuration information based on being connectedto the remote optical fiber. The configuration information may identifya network address of remote network device 206-2, a multiplexer portidentifier associated with the remote optical fiber, a wavelength and/ortime slot for optical signals transmitted by remote network device206-2, or the like.

In some implementations, remote network device 206-2 may provide theconfiguration information to local network device 206-1 (e.g., via OSC212, via network management device 202, etc.). Network devices 206-1 and206-2 may perform configuration operations based on configurationinformation associated with network devices 206-1 and 206-2. Forexample, network devices 206-1 and 206-2 may perform an Ethernet AddressResolution protocol to associate network addresses of network devices206-1 and 206-2 (e.g., IP addresses, network ports, etc.) with hardwareaddresses of network devices 206-1 and 206-2 (e.g., multiplexer ports,network device identifiers, etc.). In this way, network devices 206-1and 206-2 may determine configuration information without preemptivelyplanning the configuration information using noise optical signals. Thispermits network devices 206-1 and 206-2 to reduce time and/or expenserequired to plan configuration of optical network 204.

In some implementations, controller device 210 and/or network managementdevice 202 may determine one or more shared risk link group identifiers(SRLG identifiers) based on the configuration information. For example,controller device 210 and/or network management device 202 may aggregateconfiguration information determined by a set of network devices 206 ofoptical network 204. The aggregated configuration information mayidentify links between network devices 206. For example, the aggregatedconfiguration information may identify locations of a first networkdevice 206 and a second network device 206.

Based on the aggregated configuration information, controller device 210and/or network management device 202 may determine SRLG identifiers. Forexample, controller device 210 and/or network management device 202 mayassign a particular SRLG identifier, from a pool of available SRLGidentifiers, to a first pair of links between local network device 206-1and remote network device 206-2. As another example, controller device210 and/or network management device 202 may assign different SRLGidentifiers to a second pair of links between local network device 206-1and two other network devices 206 (e.g., other than remote networkdevice 206-2). In this way, controller device 210 and/or networkmanagement device 202 may assign SRLG identifiers to links of opticalnetwork 204 based on aggregated configuration information, which reducesa quantity of errors when assigning the SRLG identifiers and/or reducetime required to implement the SRLG identifiers.

As another example, controller device 210 may cause remote networkdevice 206-2 to transmit an optical signal in a particular direction ofa ring-based configuration. For example, if the configuration indicatesthat local network device 206-1 transmits an optical signal at awavelength of 1200 nm in a clockwise direction via a particular opticalfiber, remote controller device 210 may cause remote network device206-2 to transmit an optical signal at the wavelength of 1200 nm in acounter-clockwise direction via the particular optical fiber. In thisway, remote controller device 210 may configure network devices 206 of aring-based configuration, which improves efficiency of implementingring-based configurations in optical network 204.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIGS. 7A-7E are diagrams of an example implementation 700 relating toexample process 600 shown in FIG. 6. FIGS. 7A-7E show an example ofidentifying an optical fiber connection based on a noise signal.

As shown in FIG. 7A, and by reference number 702, controller device210-1 may determine whether remote network device 206-2 is associatedwith configuration information. The configuration information mayinclude the IP address of remote network device 206-2, informationidentifying the chassis, slot and port of transceiver 218 of remotenetwork device 206-2, and information identifying the chassis, slot, andport of the WDM (e.g., multiplexer port) to which transceiver 218 isconnected. Assume that controller device 210-1 requests configurationinformation from network management device 202, and does not receiveconfiguration information relating to remote network device 206-2 fromnetwork management device 202.

As shown by reference number 704, a technician may connect transceiver218 to an available local optical fiber. As shown by reference number706, to determine a wavelength and/or multiplexer port associated withthe available local optical fiber, transceiver 218 (e.g., transmitter220 of transceiver 218) may determine to provide power to amplifier 224without specifying a particular wavelength of optical signal togenerate. As shown by reference number 708, transmitter 220 provides thepower to amplifier 224. As shown by reference number 710, OCM 214 maydetect a wavelength of 1551.32 nm. Assume that OCM 214 providesinformation identifying the wavelength of 1551.32 nm to controllerdevice 210-1. As shown by reference number 712, controller device 210-1may determine that transceiver 218 is connected to a local optical fiberassociated with multiplexer port 3, and may determine a time at whichOCM 214 detected the optical signal.

As shown by reference number 714, controller device 210-1 may determineconfiguration information for local network device 206-1. As shown,controller device 210-1 determines an IP address of local network device206-1 (e.g., 198.75.4.2), a time slot for signals transmitted viamultiplexer port 3 (e.g., 71), a multiplexer port identifier (e.g., 3),and a device identifier of local network device 206-1 (e.g., 92304).

As shown in FIG. 7B, and by reference number 716, controller device210-1 provides the configuration information to remote network device206-2 via OSC 212. As further shown, OSC 212 of remote network device206-2 may provide the remote configuration information to controllerdevice 210-2.

As shown in FIG. 7C, and by reference number 718, controller device210-2 may receive the configuration information for local network device206-1. As shown by reference number 720, controller device 210-2 maydetermine to perform plug and play operations to configure remotenetwork device 206-2 to communicate with local network device 206-1, asdescribed in more detail below.

As shown by reference number 722, based on the connection information,transceiver 218 may be connected to a remote optical fiber associatedwith multiplexer port 3. Assume that a technician connects transceiver218 to the remote optical fiber. As shown by reference number 724,controller device 210-2 may test whether transceiver 218 is connected tothe correct remote optical fiber by causing a noise optical signal to betransmitted to the remote optical fiber. To transmit the noise opticalsignal, transceiver 218 may provide power to amplifier 224 withoutspecifying a particular wavelength.

As shown by reference number 726, amplifier 224 may receive informationindicating that an optical signal with a wavelength of 1551.32 nm isdetected (e.g., by OCM 214) at a time of 14:15:15. As shown by referencenumber 728, based on the optical signal with the wavelength of 1551.32nm and the time of 14:15:15, controller device 210-2 may determine thattransceiver 218 is connected to the correct remote optical fiber and/ormultiplexer port 3. As shown by reference number 730, controller device210-2 may determine configuration information for remote network device206-2. Here, controller device 210-2 determines an IP address of214.8.16.4, a time slot of “71,” a multiplexer port identifier of “3,”and a device identifier of remote network device 206-2 of “92396.”

As shown by reference number 732, controller device 210-2 may determinethat plug and play optical network configuration is successful (e.g.,based on local network device 206-1 and remote network device 206-2being associated with multiplexer port 3, the wavelength of 1551.32 nm,and the time slot of 71). As shown by reference number 734, controllerdevice 210-2 may provide configuration information, relating to remotenetwork device 206-2, to local network device 206-1.

As shown in FIG. 7D, and by reference number 736, controller device210-2 of remote network device 206-2 may provide, to local networkdevice 206-1, configuration information via OSC 212. In someimplementations, controller device 210-2 may provide the configurationinformation to another device (e.g., network management device 202), andthe other device may provide the configuration information to localnetwork device 206-1 and/or controller device 210-1.

As shown in FIG. 7E, network devices 206-1 and 206-2 may perform anEthernet address resolution protocol based on configuration informationassociated with network devices 206-1 and 206-2. The Ethernet addressresolution protocol may associate network addresses of network devices206-1 and 206-2 (e.g., 118.75.4.2 for local network device 206-1 and214.8.16.4 for remote network device 206-2) with device identifiers ofnetwork devices 206-1 and 206-2 (e.g., 92304 for local network device206-1 and 92396 for remote network device 206-2). As further shown,based on the Ethernet address resolution protocol and/or the plug andplay configuration operation, network devices 206-1 and 206-2 maycommunicate. In this way, network devices 206-1 and 206-2 may configureoptical network 204 based on plug and play configuration operations.This reduces effort required to plan optical network 204 and/or todetermine causes of configuration errors in relation to network device206.

As indicated above, FIGS. 7A-7E are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 7A-7E.

Implementations described herein may enable network device 206 todetermine a particular wavelength at which to transmit an optical signalvia an optical fiber. By transmitting a noise signal via the opticalfiber, network device 206 reduces an amount of time and/or effortrequired to determine the particular wavelength (e.g., based onmultiplexer 208 filtering wavelengths other than the particularwavelength). Implementations described herein may provide configurationinformation to transceiver 218, or another device, based on determiningthe particular wavelength, which improves efficiency and reduces timeconsumption when implementing network device 206, or other networkdevices 206, in an optical network 204.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, and/or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related itemsand unrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

1-20. (canceled)
 21. A method comprising: determining, by a localnetwork device, that a remote network device is not associated withconfiguration information based on the local network device beingconnected to an optical fiber; determining, by the local network device,a particular wavelength that is associated with the optical fiber basedon determining that the remote network device is not associated with theconfiguration information; and providing, by the local network device,the configuration information based on determining the particularwavelength.
 22. The method of claim 21, further comprising: determininga multiplexer port identifier that identifies a multiplexer port towhich the local network device is connected, where the configurationinformation is further provided based on determining the multiplexerport identifier.
 23. The method of claim 21, where the configurationinformation identifies the particular wavelength and a multiplexer portidentifier.
 24. The method of claim 21, where the configurationinformation includes a network address of the local network device andinformation identifying a time slot associated with the local networkdevice.
 25. The method of claim 21, where the configuration informationis provided to the remote network device via an optical supervisorychannel (OSC).
 26. The method of claim 21, where the configurationinformation is provided by the local network device to a networkmanagement device that provides the configuration information to theremote network device.
 27. The method of claim 21, further comprising:connecting a transceiver of the local network device to the opticalfiber before determining that the remote network device is notassociated with the configuration information.
 28. A local networkdevice comprising: a memory; and one or more processors to: determinethat a remote network device is not associated with configurationinformation based on the local network device being connected to anoptical fiber; determine a particular wavelength that is associated withthe optical fiber based on determining that the remote network device isnot associated with the configuration information; and provide theconfiguration information based on determining the particularwavelength.
 29. The local network device of claim 28, where the one ormore processors are further to: determine a multiplexer port identifierthat identifies a multiplexer port to which the local network device isconnected, where the configuration information is further provided basedon determining the multiplexer port identifier.
 30. The local networkdevice of claim 28, where the configuration information identifies theparticular wavelength and a multiplexer port identifier.
 31. The localnetwork device of claim 28, where the configuration information includesa network address of the local network device and informationidentifying a time slot associated with the local network device. 32.The local network device of claim 28, where the configurationinformation is provided to the remote network device via an opticalsupervisory channel (OSC).
 33. The local network device of claim 28,where the configuration information is provided by the local networkdevice to a network management device that provides the configurationinformation to the remote network device.
 34. The local network deviceof claim 28, where the one or more processors are further to: connect atransceiver of the local network device to the optical fiber beforedetermining that the remote network device is not associated with theconfiguration information.
 35. A non-transitory computer-readable mediumstoring instructions, the instructions comprising: one or moreinstructions that, when executed by a local network device, cause thelocal network device to: determine that a remote network device is notassociated with configuration information based on the local networkdevice being connected to an optical fiber; determine a particularwavelength that is associated with the optical fiber based ondetermining that the remote network device is not associated with theconfiguration information; and provide the configuration informationbased on determining the particular wavelength.
 36. The non-transitorycomputer-readable medium of claim 35, where the instructions furthercomprise: one or more instructions that, when executed by the localnetwork device, cause the local network device to: determine amultiplexer port identifier that identifies a multiplexer port to whichthe local network device is connected, where the configurationinformation is further provided based on determining the multiplexerport identifier.
 37. The non-transitory computer-readable medium ofclaim 35, where the configuration information identifies the particularwavelength and a multiplexer port identifier.
 38. The non-transitorycomputer-readable medium of claim 35, where the configurationinformation includes a network address of the local network device andinformation identifying a time slot associated with the local networkdevice.
 39. The non-transitory computer-readable medium of claim 35,where the configuration information is provided to the remote networkdevice via an optical supervisory channel (OSC).
 40. The non-transitorycomputer-readable medium of claim 35, where the instructions furthercomprise: one or more instructions that, when executed by the localnetwork device, cause the local network device to: connect a transceiverof the local network device to the optical fiber before determining thatthe remote network device is not associated with the configurationinformation.